Cooking as a malleable system

I want computing to feel like cooking.

What I like about it

I like cooking. I like how it is built on top of chemical and physical reactions, but i don't necessarily have to have a deep understanding of chemistry or physics to cook. It definitely helps to understand the chemistry, but it is not required. With cooking i feel like there is such a thing as a cooking reaction. A kind of abstraction over chemistry that one learns when learning to cook. Eggs get hard the more you cook them. I know that underneath there is a chemical reaction, yet all i need to cook eggs is an understanding of the cooking reaction.

How is it malleable

1. Once you learn the basics, it is possible to change a recipe on the fly as you are cooking it.
2. Cooking allows somewhat recombination of its different layers: you can replace eggs with flax, spices with other spices.
3. Tools and recipe are definitly easy to begin working with but can be mastered.
4. People of all experiences can cook, deciding on the spot what is made from scratch and what is made from prepared ingredients.
5. Recipes can be freely shared with others.
6. Modifiying what you cook does not depend on another skill set.
7. Cooking is a fun and empowering experience.

Takeaways

Recipes are loose algorithms, you can follow them or improvise with them. Ingredients are late-binded with what's available in your pantry. Ingredients may play different roles. The style is modifiable with spices. Prepared food exists to delegate the creation when you don't have time, money, skills or want.

I think we need recipes. Something easily shareable and that's easy to change. A sequence of loose steps that one can modify while executing them. I also think that late-binding, as seen with ingredients, is a good idea. It seems here that ingredients as a medium, along with the nice abstraction that is cooking reactions (as opposed to chemical reactions) is what makes this possible. What could be the ingredients and reactions of computing?